docs: video analysis accepts sources up to 6 minutes (and fix dubbing's missed 300 sec) - #32
Merged
Merged
Conversation
The API lowered /v1/video-analysis from 600 to 360 sec. Nothing here gates on the number -- the limit is enforced server-side -- but both READMEs and context7.json stated 600. 600 was never a real limit on the API either: a shared 360 sec probe ceiling rejected every longer source before the endpoint's own check ran, so a caller who believed the old number was uploading videos that were always going to be refused. Also fixes dubbing's cap, which this repo missed when the API raised it from 180 to 300 sec: the SDK README and the CLI README both still said 180, and a caller who believes that trims a video the API would have taken. (The 180 sec line under video_to_sound / video_to_video_sound is correct and stays.)
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
Docs-only content, but PyPI renders the README on the project page, so the corrected caps only reach readers through a release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows sonilo-api-dashboard#292, deployed to prod 2026-08-20.
video-analysis: 600 → 360 sec
/v1/video-analysislowered its source-video cap to 360 sec (6 min). Nothing in these packages gates on it — the limit is enforced server-side — but three surfaces stated 600: the SDK README, the CLI README, andcontext7.json.600 was never a real API limit: a shared 360 sec probe ceiling rejected every longer source before the endpoint's own check ran. A caller who believed the old number was uploading videos that were always going to be refused, so this is a correction as much as a cap change.
Also: dubbing's 300 sec, which this repo missed
The API raised
/v1/dubbingfrom 180 to 300 sec on 2026-08-20 (sonilo-api-dashboard#291).sonilo-mcp,sonilo-jsand the skills repo were updated; this repo was not. The SDK README and the CLI README both still said 180 — the harmful direction, since a caller who believes it trims a video the API would have taken.Left alone deliberately: the "at most 180 seconds" line under
video_to_sound/video_to_video_sound. Those endpoints did not change.Scope
Docs only — no source file touched, no version bump.
context7.jsonre-verified against the schema limits the CLI'stest_context7.pyenforces (22 rules, none over 255 chars, description 127 chars).